HAM Radio 3.2/Ham Radio Version 3.2 (Chestnut CD-ROMs)(1993).ISO/tcp/nosmail/bbsfwd.inf

Text File | 1991-05-12 | 9KB | 203 lines

                                  BBSFWD.INF

From [e-mail] Sat Nov 17 03:01:55 1990
Received: from wb0mpq.ampr.org by n2mh.ampr.org with SMTP
        id AA2277 ; Sat, 17 Nov 90 02:07:58 GMT
Date: Sat, 17 Nov 90 01:48:43 GMT
Message-Id: <[e-mail]>
From: [e-mail] (Al Shjarback - Warren,NJ 07060)
To: [e-mail]
Subject: Forwarding 1

>From nn2z@nn2z Wed Oct 10 23:09:51 1990
Received: from pc.nn2z.ampr.org by wb0mpq.ampr.org with SMTP
        id AA16293 ; Wed, 10 Oct 90 22:55:43 GMT
Received: from nn2z.ampr.org by pc.nn2z.ampr.org with SMTP
        id AA6110 ; Wed, 10 Oct 90 18:30:16 EDT
Received: by nn2z.ampr.org (5.59/smail2.5/08-26-89)
        id AA17857; Wed, 10 Oct 90 18:42:39 EDT
Received: from ucsd.edu by thumper.bellcore.com (4.1/4.7)
        id AA10039; Wed, 10 Oct 90 18:44:55 EDT
Received: by ucsd.edu; id AA11758
        sendmail 5.64/UCSD-2.1-sun
        Wed, 10 Oct 90 13:55:35 -0700 for hpbbrd!db0sao!dg4scv-2!tcp-group
Received: from sics.se by ucsd.edu; id AA11743
        sendmail 5.64/UCSD-2.1-sun via SMTP
        Wed, 10 Oct 90 13:55:27 -0700 for /usr/lib/sendmail -oc -odb
-oQ/var/spool/lqueue -oi -ftcp-group-relay tcp-group-list
Received: from isis.sics.se by sics.se (5.61-bind 1.5+ida/SiteCap-3.0)
        id AA21441; Wed, 10 Oct 90 21:55:11 +0100
Received: from localhost by isis.sics.se (5.61-bind 1.5+ida/SiteCap-3.0)
        id AA07844; Wed, 10 Oct 90 21:55:05 +0100
Message-Id: <[e-mail]>
To: [e-mail]
Cc: [e-mail]
Subject: NOS Mbox forwarding
Date: Wed, 10 Oct 90 21:55:00 +0100
From: [e-mail]

I have been hacking on the NOS mailbox recently. Paul Healy, EI9GL, wrote some
good forwarding code for NOS. I started changing Pauls code, and I am not sure
if he will recognize it now.

The NOS mailbox now supports forwarding, both outgoing forwarding and reverse
forwarding. It keeps track of which bulletins have been forwarded by adding
"X-Forwarded-To:" lines to the messages. Messages in public "areas" are sent
as bulletins, with BID and everything. Messages from private areas are treated
as private mail and are deleted after forwarding.

The message areas can be checked for messages to forward at a regular
intervals, which is set with the "mbox timer" command. Forwarding can be
started immediately with the "mbox kick" command. There is also a "mbox motd"
and a "mbox attended" command, which I picked from the G1EMM code.

There is a new command in the mailbox too, "Verbose." It displays a message
with all it header lines, contrary to "Read" which only shows four lines. It
is also possible to read a message simply by typing its number.

The mailbox reads a forwarding file, "spool/forward.bbs". Here is a sample
file:

sk0tm 0006
ax25 ax0 sk0tm
sk0tm
amsat
all
------
sm0rgv
netrom #sth675
..c sm0rgv-2
sm0rgv
amsat

The first word on the first line in a forwarding record is the name of the BBS
to forward to. This should be the same type of name which is shown by the
"mbox status" command. The second word is optional. It specifies a range when
forwarding may take place. "0006" means that there will only be forwarding to
this station between midnight and 6am.

The second line specifies how to establish the connection. It should start
with the protocol (ax25, tcp or netrom) and be followed by all the parameters
which are necessary when NOS has to establish a network connection.

Directly after the second line there may be lines that start with a dot. What
follows after the dot will be sent to the remote BBS as soon as the connection
is established.

Then follows the names of a number of message areas, public or private.
Finally, there should be a couple of '-' signs to separate one forwarding
record from another.

The code seems to be working, although there could of course be bugs left.
Anyway, the source is available with ftp from sics.se. The filename is
archive/packet/ka9q/nos/mailbox.arc.

As usual, this message is the only documentation, so it could be worth saving.

Anders

From [e-mail] Sat Nov 17 04:15:14 1990
Received: from wb0mpq.ampr.org by n2mh.ampr.org with SMTP
        id AA2278 ; Sat, 17 Nov 90 03:16:45 GMT
Date: Sat, 17 Nov 90 01:49:06 GMT
Message-Id: <[e-mail]>
From: [e-mail] (Al Shjarback - Warren,NJ 07060)
To: [e-mail]
Subject: Forwarding 2

>From nn2z@nn2z Mon Oct 15 15:08:12 1990
Received: from pc.nn2z.ampr.org by wb0mpq.ampr.org with SMTP
        id AA16697 ; Mon, 15 Oct 90 14:57:51 GMT
Received: from nn2z.ampr.org by pc.nn2z.ampr.org with SMTP
        id AA6493 ; Mon, 15 Oct 90 10:24:34 EDT
Received: by nn2z.ampr.org (5.59/smail2.5/08-26-89)
        id AA01219; Mon, 15 Oct 90 10:35:34 EDT
Received: from ucsd.edu by thumper.bellcore.com (4.1/4.7)
        id AA01720; Mon, 15 Oct 90 10:31:56 EDT
Received: by ucsd.edu; id AA00355
        sendmail 5.64/UCSD-2.1-sun
        Mon, 15 Oct 90 04:29:50 -0700 for hb9zz
Received: from sics.se by ucsd.edu; id AA00339
        sendmail 5.64/UCSD-2.1-sun via SMTP
        Mon, 15 Oct 90 04:29:38 -0700 for /usr/lib/sendmail -oc -odb
-oQ/var/spool/lqueue -oi -ftcp-group-relay tcp-group-list
Received: from sarapis.sics.se by sics.se (5.61-bind 1.5+ida/SiteCap-3.0)
        id AA09221; Mon, 15 Oct 90 12:29:26 +0100
Received: from localhost by sarapis.sics.se (5.61-bind 1.4+ida/SiteCap-3.0)
        id AA06837; Mon, 15 Oct 90 11:56:45 +0100
Message-Id: <[e-mail]>
To: "JAMES C MANKIN (814)-863-4348" <[e-mail]>
Cc: [e-mail]
Subject: Re: NOS Mbox forwarding
In-Reply-To: Your message of Sun, 14 Oct 90 15:36:00 -0400.
             <[e-mail]>
Date: Mon, 15 Oct 90 11:56:41 +0100
From: [e-mail]

James,

(I am Cc:ing this to tcp-group.)

>   Thanks, changing that line solved the problem.  Another thing I notice now
> is that the nos mailbox doesnt disconnect cleanly after forwarding, it seems
> to do a reset because the connection disappears from the ax status display
> without an ax25 disconnect packet being sent.

This is really odd, has anybody else noticed this?

>  Is there a way to send a message that is for a user at a bbs, rather than
> the bbs's owner?  I can do it if I edit the .txt file in the mail directory
> to have the To: address I want, so my problem is how does one get a message
> for kb3kj @ w3ya  to be placed in the w3ya  mail area.  There must be
> something I am overlooking.

When a message is entered to the mailbox, the address is rewritten according
to rules in the /spool/rewrite file. The first word on each line in the
rewrite file is an address using wildcards. If that address matches the
address you are trying to rewrite, it is rewritten according to the format of
the second word. If the third word is an 'r', the rewrite procedure will be
repeated, now using the new address as input.

Ok, so here is a sample /spool/rewrite file for a machine with the hostname
sk0we.ampr.org:

*!* $2@$1 r
*@sk0we.ampr.org $1 r
*@*.ampr.org $1@$2.ampr.org
sm0rgv@* sm0rgv
*@w3ya* w3ya
*@k* $1%k$[e-mail]

The first line means that addresses written in the "host!user" format should
be rewritten to "user@host" and then the rewrite procedure should be repeated.

The second line converts the address "[e-mail]" into the local
address "user" and then repeats the rewrite procedure.

The third line seems to do nothing. It just converts "[e-mail]" to
"[e-mail]". But it also exits the rewrite procedure since the line
does not end with an 'r'. Any address ending with ".ampr.org" will not be
converted further.

The line "sm0rgv@* sm0rgv" will keep mail for sm0rgv on the local machine even
if it is mistakenly addressed to another BBS, such as "sm0rgv@w3iwi". The line
will however fail to convert addresses such as "[e-mail]" because
of the line described in the previous paragraph.

The line "*@w3ya* w3ya" will leave mail for "user@w3ya" in the local message
area named "w3ya". The same goes for mail using some sort of hierarchical
routing designators such as "[e-mail]". The only exception is for
mail addressed to "[e-mail]" as described above.

The line "*@k* $1%k$[e-mail]" is an example of
how to establish an Internet "wormhole." Suppose I want to forward all mail to
stations with callsigns starting with K to W3IWI through the Internet. The
line quoted above would do it. But if the mail for "user@kxxxx" is received by
w3iwi.ampr.org with SMTP, there might be some problems because the rewrite
file is not scanned when mail is received with SMTP. This could easily be
changed however. Let me know if this is causing you any inconveniencies.

Anders